home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
FishMarket 1.0
/
FishMarket v1.0.iso
/
fishies
/
176-200
/
disk_197
/
ctags
/
ctags.cat
< prev
next >
Wrap
Text File
|
1992-05-06
|
4KB
|
129 lines
CTAGS(1) User Commands CTAGS(1)
NNAAMMEE
ctags - create a tags file
SSYYNNOOPPSSIISS
ccttaaggss [ --BBFFaattuuwwvvxx ] name ...
DDEESSCCRRIIPPTTIIOONN
_C_t_a_g_s makes a tags file for _e_x(1) from the specified C, Pas-
cal, Fortran, YACC, lex, and lisp sources. A tags file
gives the locations of specified objects (in this case func-
tions and typedefs) in a group of files. Each line of the
tags file contains the object name, the file in which it is
defined, and an address specification for the object defini-
tion. Functions are searched with a pattern, typedefs with a
line number. Specifiers are given in separate fields on the
line, separated by blanks or tabs. Using the _t_a_g_s file, _e_x
can quickly find these objects definitions.
If the --xx flag is given, _c_t_a_g_s produces a list of object
names, the line number and file name on which each is
defined, as well as the text of that line and prints this on
the standard output. This is a simple index which can be
printed out as an off-line readable function index.
If the --vv flag is given, an index of the form expected by
_v_g_r_i_n_d(1) is produced on the standard output. This listing
contains the function name, file name, and page number
(assuming 64 line pages). Since the output will be sorted
into lexicographic order, it may be desired to run the out-
put through ssoorrtt --ff. Sample use:
ctags -v files | sort -f > index
vgrind -x index
Files whose names end in ..cc or ..hh are assumed to be C source
files and are searched for C routine and macro definitions.
Files whose names end in ..yy are assumed to be YACC source
files. Files whose names end in ..ll are assumed to be either
lisp files if their first non-blank character is `;', `(',
or `[', or lex files otherwise. Other files are first exam-
ined to see if they contain any Pascal or Fortran routine
definitions; if not, they are processed again looking for C
definitions.
Other options are:
--FF use forward searching patterns (/.../) (default).
--BB use backward searching patterns (?...?).
--aa append to tags file.
Formatted 88/12/30 25 August 1982 1
CTAGS(1) User Commands CTAGS(1)
--tt create tags for typedefs.
--ww suppressing warning diagnostics.
--uu causing the specified files to be _u_p_d_a_t_e_d in tags, that
is, all references to them are deleted, and the new
values are appended to the file. (Beware: this option is
implemented in a way which is rather slow; it is usually
faster to simply rebuild the _t_a_g_s file.)
The tag _m_a_i_n is treated specially in C programs. The tag
formed is created by prepending _M to the name of the file,
with a trailing .c removed, if any, and leading pathname
components also removed. This makes use of _c_t_a_g_s practical
in directories with more than one program.
FFIILLEESS
tags output tags file
SSEEEE AALLSSOO
ex(1), vi(1)
AAUUTTHHOORR
Ken Arnold; FORTRAN added by Jim Kleckner; Bill Joy added
Pascal and --xx,, replacing _c_x_r_e_f_; C typedefs added by Ed
Pelegri-Llopart.
BBUUGGSS
Recognition of ffuunnccttiioonnss, ssuubbrroouuttiinneess and pprroocceedduurreess for
FORTRAN and Pascal is done is a very simpleminded way. No
attempt is made to deal with block structure; if you have
two Pascal procedures in different blocks with the same name
you lose.
The method of deciding whether to look for C or Pascal and
FORTRAN functions is a hack.
Does not know about #ifdefs.
Should know about Pascal types. Relies on the input being
well formed to detect typedefs. Use of -tx shows only the
last line of typedefs.
Formatted 88/12/30 25 August 1982 2